Skip to content

⬆️ Update dependency postcss-nesting to v14#213

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/postcss-nesting-14.x
Open

⬆️ Update dependency postcss-nesting to v14#213
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/postcss-nesting-14.x

Conversation

@renovate

@renovate renovate Bot commented Jan 14, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
postcss-nesting (source) ^12.0.1 → ^14.0.0 age confidence

Release Notes

csstools/postcss-plugins (postcss-nesting)

v14.0.0

Compare Source

January 14, 2026

v13.0.2

Compare Source

June 10, 2025

v13.0.1

Compare Source

October 23, 2024

v13.0.0

Compare Source

August 3, 2024

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@vercel

vercel Bot commented Jan 14, 2026 •
edited
Loading

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
base Error Error Jul 19, 2026 8:50pm

@bolt-new-by-stackblitz

bolt-new-by-stackblitz Bot commented Jan 14, 2026

Copy link
Copy Markdown

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@renovate
renovate Bot force-pushed the renovate/postcss-nesting-14.x branch from 9d86443 to ee36ebe Compare February 2, 2026 15:49
@renovate
renovate Bot force-pushed the renovate/postcss-nesting-14.x branch from ee36ebe to 76d9064 Compare May 12, 2026 14:12
@renovate
renovate Bot force-pushed the renovate/postcss-nesting-14.x branch from 76d9064 to 70cfed1 Compare June 11, 2026 10:03
@renovate
renovate Bot force-pushed the renovate/postcss-nesting-14.x branch from 70cfed1 to 3c49cd1 Compare July 12, 2026 14:46
@renovate
renovate Bot force-pushed the renovate/postcss-nesting-14.x branch from 3c49cd1 to a946c8b Compare July 15, 2026 03:32
@renovate
renovate Bot force-pushed the renovate/postcss-nesting-14.x branch from a946c8b to 4baa181 Compare July 15, 2026 23:29
@renovate
renovate Bot force-pushed the renovate/postcss-nesting-14.x branch from 4baa181 to 3ae5b77 Compare July 16, 2026 02:42
@renovate
renovate Bot force-pushed the renovate/postcss-nesting-14.x branch from 3ae5b77 to c98b4ac Compare July 16, 2026 06:58
@renovate
renovate Bot force-pushed the renovate/postcss-nesting-14.x branch from c98b4ac to 57f81ca Compare July 16, 2026 11:45
@renovate
renovate Bot force-pushed the renovate/postcss-nesting-14.x branch from 57f81ca to ac3f29a Compare July 17, 2026 03:47
@renovate
renovate Bot force-pushed the renovate/postcss-nesting-14.x branch from ac3f29a to 685094e Compare July 19, 2026 20:50
@renovate

renovate Bot commented Jul 19, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
? Verifying lockfile against supply-chain policies (506 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 11, reused 0, downloaded 0, added 0
Progress: resolved 62, reused 0, downloaded 0, added 0
✗ Lockfile failed supply-chain policy check (506 entries in 3.3s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  [email protected] was published at 2026-07-19T08:44:18.000Z, within the minimumReleaseAge cutoff (2026-07-18T20:50:45.842Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.
Progress: resolved 311, reused 0, downloaded 1, added 0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants